cleanup and snakenull for handling missing entities #149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snakenull is a new snakebids feature described here: khanlab/snakebids#470 in response to the issue raised here khanlab/snakebids#469
It adds flexibility to input datasets. For example, if run-X exists in some subjects but not others, it will keep the
runentity as a wildcard, and infill X assnakenullfor all cases that didn't already have it defined. Note that the default behaviour is still to have snakenull disabled, so here we enable it (globally, but we could just as easily enable it for a given pybids_input) in your snakebids.yml config file.Also note that for this build to work, we will need to include snakenull in our dependencies. Currently I'm working with a local build and my test runs are working. To deploy correctly, we can either wait until this feature is merged and specify its new version number as our snakebids requirement, or we can use
git+to point to the branch (this would be a temporary fix as the branch will be deleted once merged).This PR also clean up some files that should never have been included (.vscode, __pycache__, and .snakemake - which were most likely committed by mistake during development and testing)